home *** CD-ROM | disk | FTP | other *** search
- Path: pt9256.ped.pto.ford.com!tumkur
- From: tumkur@pt9256.ped.pto.ford.com (Ramkumar Tumkur)
- Newsgroups: comp.lang.c++
- Subject: Re: C++ Exceptions and error codes
- Date: 12 Mar 1996 19:19:13 GMT
- Organization: Ford Motor Co., Powertrain Electronics
- Message-ID: <4i4inh$pca@pt9201.ped.pto.ford.com>
- References: <313BC8AA.1B24@cais.com>
- NNTP-Posting-Host: pt9256.ped.pto.ford.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Nehal Trivedi (ntrivedi@cais.com) wrote:
- : I am looking for expert suggestions on designing C++ exception classes for
- : error-handling in client-server systems with the following constraints:
- : 1) Need to handle the equivalent of 100+ error codes
- : 2) Need to handle exceptions thrown by:
- : a) OODB (ObjectStore)
- : b) ORB (Orbix)
- : c) STL (Objectspace)
- : 3) Need to handle internationalization of error messages
-
- : I have done error-handling and some exception handling before, so I am not
- : completely new to this. Also by now I have gone through all the C++ books that I
- : could find on the subject.
-
- : Thanks
- : Nehal Trivedi
- : (ntrivedi@cais.com)
- : (ntrivedi@manu.com)
-
- You might already know about this. Harald M Muller's "Ten Rules for
- Handling Exception Handling Successfully" in C++ Report of Jan 96
- is an exceptionally well written and formalized article. You should
- read this before you formulate your specs. As is the Exception
- Handling system in C++, so are the resources available regarding
- it - sticky and sparse.
-
- ramu
-